|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved standards track document.
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendation uses the internet message format as defined in the reference.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=5322
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Draft Standard approved 2008-10. Updated by RFC 6854. Obsoletes RFC 2822. Updates RFC 4021. Errata exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
See 5. above.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item 8.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
---------------------------/
/
[ANSI.X3-4.1986] American National Standards Institute, "Coded/
Character Set - 7-bit American Standard Code for/
Information Interchange", ANSI X3.4, 1986./
/
[RFC1034] Mockapetris, P., "Domain names - concepts and/
facilities", STD 13, RFC 1034, November 1987./
/
[RFC1035] Mockapetris, P., "Domain names - implementation and/
specification", STD 13, RFC 1035, November 1987./
/
[RFC1123] Braden, R., "Requirements for Internet Hosts -/
Application and Support", STD 3, RFC 1123,/
October 1989./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for/
Syntax Specifications: ABNF", STD 68, RFC 5234,/
January 2008./
/
Informative References/
-----------------------------/
/
[RFC0822] Crocker, D., "Standard for the format of ARPA/
Internet text messages", STD 11, RFC 822,/
August 1982./
/
[RFC1305] Mills, D., "Network Time Protocol (Version 3)/
Specification, Implementation", RFC 1305,/
March 1992./
/
[ISO.2022.1994] International Organization for Standardization,/
"Information technology - Character code structure/
and extension techniques", ISO Standard 2022, 1994./
/
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet/
Mail Extensions (MIME) Part One: Format of Internet/
Message Bodies", RFC 2045, November 1996./
/
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet/
Mail Extensions (MIME) Part Two: Media Types",/
RFC 2046, November 1996./
/
[RFC2047] Moore, K., "MIME (Multipurpose Internet Mail/
Extensions) Part Three: Message Header Extensions/
for Non-ASCII Text", RFC 2047, November 1996./
/
[RFC2049] Freed, N. and N. Borenstein, "Multipurpose Internet/
Mail Extensions (MIME) Part Five: Conformance/
Criteria and Examples", RFC 2049, November 1996./
/
[RFC2822] Resnick, P., "Internet Message Format", RFC 2822,/
April 2001./
/
[RFC3864] Klyne, G., Nottingham, M., and J. Mogul,/
"Registration Procedures for Message Header/
Fields", BCP 90, RFC 3864, September 2004./
/
[RFC4021] Klyne, G. and J. Palme, "Registration of Mail and/
MIME Header Fields", RFC 4021, March 2005./
/
[RFC4288] Freed, N. and J. Klensin, "Media Type/
Specifications and Registration Procedures",/
BCP 13, RFC 4288, December 2005./
/
[RFC4289] Freed, N. and J. Klensin, "Multipurpose Internet/
Mail Extensions (MIME) Part Four: Registration/
Procedures", BCP 13, RFC 4289, December 2005./
/
[RFC5321] Klensin, J., "Simple Mail Transfer Protocol",/
RFC 5321, October 2008.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
